QueryBuilder: prevent misuse of DELETE with LIMIT#12068
Merged
greg0ire merged 1 commit intodoctrine:3.6.xfrom Jul 12, 2025
Merged
QueryBuilder: prevent misuse of DELETE with LIMIT#12068greg0ire merged 1 commit intodoctrine:3.6.xfrom
greg0ire merged 1 commit intodoctrine:3.6.xfrom
Conversation
greg0ire
reviewed
Jul 10, 2025
greg0ire
reviewed
Jul 10, 2025
This fixes a dangerous bug where LIMIT is silently ignored in DELETE
operations, potentially causing developers to delete all rows instead
of just the intended subset. The setMaxResults() method would be
silently omitted from the final query, making operations like
delete last entry accidentally delete entire tables.
06ce8b0 to
79d4cfd
Compare
greg0ire
approved these changes
Jul 11, 2025
SenseException
approved these changes
Jul 11, 2025
Member
|
Thanks @janedbal ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Imagine you want to delete just last entry, but all your rows disappear:
I believe Doctrine should protect developers from doing destructive operations by not silently omitting crucial part of query builder (
LIMIT, although namedsetMaxResults).